fix: update all naming instances to request commerce #9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
WalkthroughThe pull request implements a comprehensive rebranding effort, renaming the application from "EasyInvoice" to "Request Commerce" across the codebase. Changes include updating package metadata, page titles and descriptions, UI component branding text, warning messages, and database schema table name prefixes. No functional logic or control flow modifications are introduced. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
Comment |
rodrigopavezi
approved these changes
Jan 5, 2026
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
Fix all issues with AI Agents 🤖
In @src/lib/constants/ecommerce.ts:
- Around line 1-3: The DEFAULT_CLIENT_ID_DOMAIN constant currently defaults to
the unreachable "https://commerce.request.network", which will break runtime DNS
calls; update DEFAULT_CLIENT_ID_DOMAIN (in src/lib/constants/ecommerce.ts) to
either revert to the previous working default domain or remove the hardcoded
fallback so it only uses process.env.NEXT_PUBLIC_DEFAULT_ECOMMERCE_DOMAIN and
fails fast, and then verify any usages in app-kit.tsx and ecommerce.ts continue
to receive a valid domain or handle missing env by throwing a clear
initialization error; ensure the replacement domain is DNS-resolvable and update
tests/configs that assume the old value.
In @src/server/db/schema.ts:
- Line 17: createTable in schema.ts changed the DB prefix from easyinvoice_ to
rncommerce_, but you must add a migration and update drizzle.config.ts to match;
create a migration file that renames existing tables (e.g., ALTER TABLE
easyinvoice_X RENAME TO rncommerce_X for each table or create new rncommerce_*
tables and copy data then drop old ones) and commit it, and update the
prefix/driver settings in drizzle.config.ts to use rncommerce_ so runtime table
lookups align with the new createTable prefix; ensure the migration is
idempotent and tested locally against a dev DB before merging.
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (19)
package.jsonsrc/app/(auth)/signin/page.tsxsrc/app/(dashboard)/i/[id]/page.tsxsrc/app/(dashboard)/invoices/[ID]/_components/payment-section.tsxsrc/app/(dashboard)/invoices/[ID]/page.tsxsrc/app/(dashboard)/payouts/batch/page.tsxsrc/app/(dashboard)/payouts/direct/page.tsxsrc/app/(dashboard)/payouts/page.tsxsrc/app/(dashboard)/payouts/recurring/create/page.tsxsrc/app/(dashboard)/payouts/recurring/page.tsxsrc/app/(dashboard)/s/[id]/page.tsxsrc/app/layout.tsxsrc/app/not-found.tsxsrc/components/app-kit.tsxsrc/components/footer.tsxsrc/components/header.tsxsrc/components/invoice/invoice-form/invoice-form.tsxsrc/lib/constants/ecommerce.tssrc/server/db/schema.ts
🧰 Additional context used
📓 Path-based instructions (1)
**/*
⚙️ CodeRabbit configuration file
**/*: - Only comment on issues that would block merging — ignore minor or stylistic concerns.
- Restrict feedback to errors, security risks, or functionality-breaking problems.
- Do not post comments on code style, formatting, or non-critical improvements.
- Keep reviews short: flag only issues that make the PR unsafe to merge.
- Limit review comments to 3–5 items maximum, unless additional blockers exist.
- Group similar issues into a single comment instead of posting multiple notes.
- Skip repetition — if a pattern repeats, mention it once at a summary level only.
- Do not add general suggestions; focus strictly on merge-blocking concerns.
- If there are no critical problems, respond with minimal approval (e.g., 'Looks good'). Do not add additional review.
- Avoid line-by-line commentary unless it highlights a critical bug or security hole.
- Highlight only issues that could cause runtime errors, data loss, or severe maintainability issues.
- Ignore minor optimization opportunities — focus solely on correctness and safety.
- Provide a top-level summary of critical blockers rather than detailed per-line notes.
- Comment only when the issue must be resolved before merge — otherwise, remain silent.
- When in doubt, err on the side of fewer comments — brevity and blocking issues only.
- Avoid posting any refactoring issues
Files:
src/app/(dashboard)/payouts/batch/page.tsxsrc/components/footer.tsxsrc/app/(dashboard)/payouts/recurring/page.tsxsrc/components/header.tsxsrc/server/db/schema.tspackage.jsonsrc/app/(auth)/signin/page.tsxsrc/app/not-found.tsxsrc/components/app-kit.tsxsrc/lib/constants/ecommerce.tssrc/app/(dashboard)/invoices/[ID]/_components/payment-section.tsxsrc/components/invoice/invoice-form/invoice-form.tsxsrc/app/(dashboard)/payouts/recurring/create/page.tsxsrc/app/(dashboard)/s/[id]/page.tsxsrc/app/layout.tsxsrc/app/(dashboard)/invoices/[ID]/page.tsxsrc/app/(dashboard)/payouts/direct/page.tsxsrc/app/(dashboard)/payouts/page.tsxsrc/app/(dashboard)/i/[id]/page.tsx
🧬 Code graph analysis (1)
src/app/layout.tsx (1)
src/components/version-badge.tsx (1)
VersionDisplay(8-18)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Build
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes:
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.